Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cbd7e6da15737fb6088320b96b5cb5fa84ba176de77343d0b3e8a422a50c821

Tx prefix hash: 0088f3418552e56547809974dc43c52e9a5c930c01a555799ef19d80273c215a
Tx public key: 64ff1c210e05dcbe243bba620f7a6d63c628dee4ddb4fa1c13dcb9e4d41dc3fe
Timestamp: 1760186932 Timestamp [UCT]: 2025-10-11 12:48:52 Age [y:d:h:m:s]: 00:077:02:37:51
Block: 1387609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55211 RingCT/type: yes/0
Extra: 0164ff1c210e05dcbe243bba620f7a6d63c628dee4ddb4fa1c13dcb9e4d41dc3fe02110000000214e4598c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3e58202a1e516b80b182bbdac0acd972a33af70f0535e2170629d62f0d1281 0.600000000000 1875804 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": 1387619, "vin": [ { "gen": { "height": 1387609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3e58202a1e516b80b182bbdac0acd972a33af70f0535e2170629d62f0d1281" } } ], "extra": [ 1, 100, 255, 28, 33, 14, 5, 220, 190, 36, 59, 186, 98, 15, 122, 109, 99, 198, 40, 222, 228, 221, 180, 250, 28, 19, 220, 185, 228, 212, 29, 195, 254, 2, 17, 0, 0, 0, 2, 20, 228, 89, 140, 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