Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb1f8152d31a512c6ca3b7fce10a32965f9525029a760cdab3f13d9ebee06b9b

Tx prefix hash: 74bd3b681e9ad88583bbd4a535b58def18a4c19ac507f1ec3e9349aa84d9147e
Tx public key: 0c5df735440dd29a380964e4dd1d33b8ed97666e7f1ecf4a0701c50bb9ab361c
Timestamp: 1709467746 Timestamp [UCT]: 2024-03-03 12:09:06 Age [y:d:h:m:s]: 01:105:18:54:31
Block: 970250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336542 RingCT/type: yes/0
Extra: 010c5df735440dd29a380964e4dd1d33b8ed97666e7f1ecf4a0701c50bb9ab361c0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ba936724e26efa0595973c95ddc92559b6da117964fc7ad15c4f835270b094e 0.600000000000 1430101 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": 970260, "vin": [ { "gen": { "height": 970250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ba936724e26efa0595973c95ddc92559b6da117964fc7ad15c4f835270b094e" } } ], "extra": [ 1, 12, 93, 247, 53, 68, 13, 210, 154, 56, 9, 100, 228, 221, 29, 51, 184, 237, 151, 102, 110, 127, 30, 207, 74, 7, 1, 197, 11, 185, 171, 54, 28, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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