Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc46742c95df691670fe21398ff49c8446c084baad11c78dac5992d80e1b6bbb

Tx prefix hash: 35528f16569e880563100e8a3543d32aa13b61db3ca52d79ee8bc85a18cb85c8
Tx public key: f8c8a7bb3545d933fd0c3ceaeab1e2d9f255099fe540af1c1810e855cf96c75c
Timestamp: 1762651711 Timestamp [UCT]: 2025-11-09 01:28:31 Age [y:d:h:m:s]: 00:056:02:45:57
Block: 1408029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40191 RingCT/type: yes/0
Extra: 01f8c8a7bb3545d933fd0c3ceaeab1e2d9f255099fe540af1c1810e855cf96c75c0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e2f9c5f86ef8df3ccad975a7d4236d3632236aeedda9b1680209366dffa4d5a 0.600000000000 1896454 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": 1408039, "vin": [ { "gen": { "height": 1408029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e2f9c5f86ef8df3ccad975a7d4236d3632236aeedda9b1680209366dffa4d5a" } } ], "extra": [ 1, 248, 200, 167, 187, 53, 69, 217, 51, 253, 12, 60, 234, 234, 177, 226, 217, 242, 85, 9, 159, 229, 64, 175, 28, 24, 16, 232, 85, 207, 150, 199, 92, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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