Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7e00fc4bc3dd6448e5ef4d595331b07b55bc8567885f26f26502e66f77f155

Tx prefix hash: 0d68098edb02961e5f177e2061d933bfc12a86f445de5556c23d0334e2d71827
Tx public key: f8946333b8c865b026f5086a85025ef632edb5e8e946e62bee352bf3e4b1e524
Timestamp: 1709544183 Timestamp [UCT]: 2024-03-04 09:23:03 Age [y:d:h:m:s]: 01:100:02:57:03
Block: 970885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332557 RingCT/type: yes/0
Extra: 01f8946333b8c865b026f5086a85025ef632edb5e8e946e62bee352bf3e4b1e52402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6b43c095b696fc0c3e3ea34bf8771e97660ebb758c099254587ab3f88589324 0.600000000000 1430748 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": 970895, "vin": [ { "gen": { "height": 970885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6b43c095b696fc0c3e3ea34bf8771e97660ebb758c099254587ab3f88589324" } } ], "extra": [ 1, 248, 148, 99, 51, 184, 200, 101, 176, 38, 245, 8, 106, 133, 2, 94, 246, 50, 237, 181, 232, 233, 70, 230, 43, 238, 53, 43, 243, 228, 177, 229, 36, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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