Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7c2fbf1530eb21bb00b3ecda49b68ab5e79396bf42ea4c0dc0df20e98db15a

Tx prefix hash: d35ff334e9b38ded9c2854ebe093b8444e2524dcdf320926600c4aca0e7e8bb3
Tx public key: a6f6776b94aca2d05b7aca838d279423c11fb5d665ffd2eaada24a1ae1ff8c21
Timestamp: 1713697568 Timestamp [UCT]: 2024-04-21 11:06:08 Age [y:d:h:m:s]: 00:350:18:36:38
Block: 1005300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250751 RingCT/type: yes/0
Extra: 01a6f6776b94aca2d05b7aca838d279423c11fb5d665ffd2eaada24a1ae1ff8c210211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e4d74a16218418b94ea63059145cf486d856aeefdfa4fafda2ebe00cfc10288 0.600000000000 1465886 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": 1005310, "vin": [ { "gen": { "height": 1005300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e4d74a16218418b94ea63059145cf486d856aeefdfa4fafda2ebe00cfc10288" } } ], "extra": [ 1, 166, 246, 119, 107, 148, 172, 162, 208, 91, 122, 202, 131, 141, 39, 148, 35, 193, 31, 181, 214, 101, 255, 210, 234, 173, 162, 74, 26, 225, 255, 140, 33, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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