Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dc43980c93d3d807902cd66aab6c35129b17cc8bcedbb982afff5918c0479793

Tx prefix hash: c1a72ca16bc0385a1755248c069ae5711c208c59f7a756601a95cf8ef60577ef
Tx public key: b0b4c84ae22a8baebd3b5c6a02052faeb28a5e3f4d1dabe57ab9fbd8880161ab
Timestamp: 1761670194 Timestamp [UCT]: 2025-10-28 16:49:54 Age [y:d:h:m:s]: 00:066:22:05:20
Block: 1399910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47917 RingCT/type: yes/0
Extra: 01b0b4c84ae22a8baebd3b5c6a02052faeb28a5e3f4d1dabe57ab9fbd8880161ab021100000006df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be3b58ffd7cd1ff9758ad563663ef220edccad7a62b6345c0e4919b021d5d55d 0.600000000000 1888217 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1399920, "vin": [ { "gen": { "height": 1399910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be3b58ffd7cd1ff9758ad563663ef220edccad7a62b6345c0e4919b021d5d55d" } } ], "extra": [ 1, 176, 180, 200, 74, 226, 42, 139, 174, 189, 59, 92, 106, 2, 5, 47, 174, 178, 138, 94, 63, 77, 29, 171, 229, 122, 185, 251, 216, 136, 1, 97, 171, 2, 17, 0, 0, 0, 6, 223, 90, 36, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8