Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a8ca5a7427c7d63d8ab3a0412f3e8f94a1aae46a748185f274ee6e76232b8b

Tx prefix hash: da7efb9eafa21e6264f3dc28eb9ebb7207a28c7767cdd6dbb161c2f706687d68
Tx public key: 71216d1090f36f48818f436e06eafca2840e3ce03751b3095758241de58a6cd0
Timestamp: 1713009827 Timestamp [UCT]: 2024-04-13 12:03:47 Age [y:d:h:m:s]: 01:216:00:38:54
Block: 999590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413073 RingCT/type: yes/0
Extra: 0171216d1090f36f48818f436e06eafca2840e3ce03751b3095758241de58a6cd00211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c296f5258e6cbea898b407f5bbc512e88a98b72e8b6b1d741c9eb80fe098ae85 0.600000000000 1460072 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": 999600, "vin": [ { "gen": { "height": 999590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c296f5258e6cbea898b407f5bbc512e88a98b72e8b6b1d741c9eb80fe098ae85" } } ], "extra": [ 1, 113, 33, 109, 16, 144, 243, 111, 72, 129, 143, 67, 110, 6, 234, 252, 162, 132, 14, 60, 224, 55, 81, 179, 9, 87, 88, 36, 29, 229, 138, 108, 208, 2, 17, 0, 0, 0, 1, 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