Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646da6d0d006ae9c87c008d74cbf7d403b22837b8bf5c46a03292248db26d54f

Tx prefix hash: e1cf7dc8e7599f3c1bba50fcddb349f5b3fd47249f29d8c7fb19357cb60836e9
Tx public key: 33d3c36310dafb778e0d6326260a289d669846456fc6c0bd65ea22e38356f1b8
Timestamp: 1638250148 Timestamp [UCT]: 2021-11-30 05:29:08 Age [y:d:h:m:s]: 03:071:06:18:17
Block: 385163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 829604 RingCT/type: yes/0
Extra: 0133d3c36310dafb778e0d6326260a289d669846456fc6c0bd65ea22e38356f1b8021100000001f6cc1430000000000000000000

1 output(s) for total of 32.494553086000 dcy

stealth address amount amount idx
00: e1acbda8ff152919dbfcf1a4b3e32bb0eb514e06410993da4f963947650f3561 32.494553086000 777292 of 0

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": 385173, "vin": [ { "gen": { "height": 385163 } } ], "vout": [ { "amount": 32494553086, "target": { "key": "e1acbda8ff152919dbfcf1a4b3e32bb0eb514e06410993da4f963947650f3561" } } ], "extra": [ 1, 51, 211, 195, 99, 16, 218, 251, 119, 142, 13, 99, 38, 38, 10, 40, 157, 102, 152, 70, 69, 111, 198, 192, 189, 101, 234, 34, 227, 131, 86, 241, 184, 2, 17, 0, 0, 0, 1, 246, 204, 20, 48, 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