Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 350ae35e79570c01e21210f6ea2b61b249df0f660c9ec9394b27e2bb39c30db3

Tx prefix hash: 044c25f5042a06372bcd9ac806b8959218a659904f454937f4475c3be2615e4c
Tx public key: 0d520ee72fd81b2a1739ecb996803cd3c64bd3c03bb6a083a429b1967453b520
Timestamp: 1736695872 Timestamp [UCT]: 2025-01-12 15:31:12 Age [y:d:h:m:s]: 00:157:04:54:17
Block: 1195832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112052 RingCT/type: yes/0
Extra: 010d520ee72fd81b2a1739ecb996803cd3c64bd3c03bb6a083a429b1967453b5200211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8723211c6b3d8cc54810ab9463c57f90f0a1b8c1f70d9c60e111a5c7739f5afc 0.600000000000 1682425 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": 1195842, "vin": [ { "gen": { "height": 1195832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8723211c6b3d8cc54810ab9463c57f90f0a1b8c1f70d9c60e111a5c7739f5afc" } } ], "extra": [ 1, 13, 82, 14, 231, 47, 216, 27, 42, 23, 57, 236, 185, 150, 128, 60, 211, 198, 75, 211, 192, 59, 182, 160, 131, 164, 41, 177, 150, 116, 83, 181, 32, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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