Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda3f5aad6fa7b10173f7a866ebf780c0d619f6f69cf2ab1530c14696d097e67

Tx prefix hash: a88ac0e4d0c7f10b4b9f6afa095e6d6bc6bb7cfd9b276c4f457f74a7f0114f63
Tx public key: d0ac381a49126f02d2d0b226fa63d06879a7f7a8dcb26bb47fb09a519247a026
Timestamp: 1578243119 Timestamp [UCT]: 2020-01-05 16:51:59 Age [y:d:h:m:s]: 05:297:13:57:16
Block: 39329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360282 RingCT/type: yes/0
Extra: 01d0ac381a49126f02d2d0b226fa63d06879a7f7a8dcb26bb47fb09a519247a0260211000000e12264afe6000000000000000000

1 output(s) for total of 454.660835183000 dcy

stealth address amount amount idx
00: 434ffaac8025dd0c9439e81fa155256567feaefaafca2d8491847fc91d4ebfa5 454.660835183000 67743 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": 39339, "vin": [ { "gen": { "height": 39329 } } ], "vout": [ { "amount": 454660835183, "target": { "key": "434ffaac8025dd0c9439e81fa155256567feaefaafca2d8491847fc91d4ebfa5" } } ], "extra": [ 1, 208, 172, 56, 26, 73, 18, 111, 2, 210, 208, 178, 38, 250, 99, 208, 104, 121, 167, 247, 168, 220, 178, 107, 180, 127, 176, 154, 81, 146, 71, 160, 38, 2, 17, 0, 0, 0, 225, 34, 100, 175, 230, 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