Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4b72a017e44dcdf9190d65dcdf6a1072cdda2d94d0d5af43545b617438cb177

Tx prefix hash: b2a39cfb4835c8806bba87fc45e15634b665d6ae9b564a8c32a0d70066ae46ae
Tx public key: cfbd57262bcebfdcabbfe3f8648e09747270278527167f934de7b0ba7a9cd961
Timestamp: 1720398423 Timestamp [UCT]: 2024-07-08 00:27:03 Age [y:d:h:m:s]: 00:274:00:40:01
Block: 1060856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195773 RingCT/type: yes/0
Extra: 01cfbd57262bcebfdcabbfe3f8648e09747270278527167f934de7b0ba7a9cd96102110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d1e4f8bfd0cc4e9e2656ab08d2878a202a533f6627d3b6a541b68fd21b0eec7 0.600000000000 1531343 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": 1060866, "vin": [ { "gen": { "height": 1060856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d1e4f8bfd0cc4e9e2656ab08d2878a202a533f6627d3b6a541b68fd21b0eec7" } } ], "extra": [ 1, 207, 189, 87, 38, 43, 206, 191, 220, 171, 191, 227, 248, 100, 142, 9, 116, 114, 112, 39, 133, 39, 22, 127, 147, 77, 231, 176, 186, 122, 156, 217, 97, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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