Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1e69aafb6b8f9cfee8565192d0b863c506b032710eafe84bba1125c5dbb118

Tx prefix hash: 4b136bf63df2701446cae4962235224311c004855da399cacfe81c69519c07a9
Tx public key: 22f20a09df3cf01aad38e2faf2fff3526f9001637d9bb47b50d5d52a5cb15ed8
Timestamp: 1712995342 Timestamp [UCT]: 2024-04-13 08:02:22 Age [y:d:h:m:s]: 00:318:16:25:57
Block: 999465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227823 RingCT/type: yes/0
Extra: 0122f20a09df3cf01aad38e2faf2fff3526f9001637d9bb47b50d5d52a5cb15ed80211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 668d26b3a50d616e331c9a6c25e4e8c82dbd1fd472a40c8abca1eb65631273c7 0.600000000000 1459945 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": 999475, "vin": [ { "gen": { "height": 999465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "668d26b3a50d616e331c9a6c25e4e8c82dbd1fd472a40c8abca1eb65631273c7" } } ], "extra": [ 1, 34, 242, 10, 9, 223, 60, 240, 26, 173, 56, 226, 250, 242, 255, 243, 82, 111, 144, 1, 99, 125, 155, 180, 123, 80, 213, 213, 42, 92, 177, 94, 216, 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