Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75f77d0e65890289a7f82cc5ee6be338fc16b2a13a3d2a08c55dbf9ffd77c9f

Tx prefix hash: 2862c8deb5f530cb50f0dff8a744317b7218175c69f681d2c9abf96a49c68a10
Tx public key: 70e640a2b6a881f03c7556160801d77ee53f6a58907ca77ef1aefbd546e17a4d
Timestamp: 1766271958 Timestamp [UCT]: 2025-12-20 23:05:58 Age [y:d:h:m:s]: 00:000:12:36:13
Block: 1438041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367 RingCT/type: yes/0
Extra: 0170e640a2b6a881f03c7556160801d77ee53f6a58907ca77ef1aefbd546e17a4d0211000000087b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 331a42214257b02e07404c53e9dc0603352ceef1571333f0c59ea7f27db0607d 0.600000000000 1926856 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": 1438051, "vin": [ { "gen": { "height": 1438041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "331a42214257b02e07404c53e9dc0603352ceef1571333f0c59ea7f27db0607d" } } ], "extra": [ 1, 112, 230, 64, 162, 182, 168, 129, 240, 60, 117, 86, 22, 8, 1, 215, 126, 229, 63, 106, 88, 144, 124, 167, 126, 241, 174, 251, 213, 70, 225, 122, 77, 2, 17, 0, 0, 0, 8, 123, 30, 81, 172, 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