Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6cd382186498de483c4e5cf4bbccd98951a37ec640d0a323c09b328cd0357f4

Tx prefix hash: 98806189614fdd2e2992e3269bcfb59a9d34bb2616629f2e9e91c1721e2eeddb
Tx public key: 5ff7be5f930edb10e7be23577a16b767dd0e8c2a09b0924d7579e73c7b66276d
Timestamp: 1746288448 Timestamp [UCT]: 2025-05-03 16:07:28 Age [y:d:h:m:s]: 00:202:00:48:47
Block: 1274979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142100 RingCT/type: yes/0
Extra: 015ff7be5f930edb10e7be23577a16b767dd0e8c2a09b0924d7579e73c7b66276d0211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4febc20b49015bdd904f46fcf02f8f5574175d059a7df41f8026f39ed306a2f8 0.600000000000 1762282 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": 1274989, "vin": [ { "gen": { "height": 1274979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4febc20b49015bdd904f46fcf02f8f5574175d059a7df41f8026f39ed306a2f8" } } ], "extra": [ 1, 95, 247, 190, 95, 147, 14, 219, 16, 231, 190, 35, 87, 122, 22, 183, 103, 221, 14, 140, 42, 9, 176, 146, 77, 117, 121, 231, 60, 123, 102, 39, 109, 2, 17, 0, 0, 0, 6, 31, 144, 81, 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