Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba426e972c1dfcaff3057136761c74e016e4960f458cab340b19e7a6f342418e

Tx prefix hash: cc3abf831f185ff6977bdc35e0f0342198749654f0cc39bd3f7c76c94764c989
Tx public key: b6708062f3175017b4d941c4cd108dc01f5fbe460dcfa46a42d922b0e76b5211
Timestamp: 1577458202 Timestamp [UCT]: 2019-12-27 14:50:02 Age [y:d:h:m:s]: 04:328:21:52:45
Block: 32913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124206 RingCT/type: yes/0
Extra: 01b6708062f3175017b4d941c4cd108dc01f5fbe460dcfa46a42d922b0e76b521102110000004be39b962a000000000000000000

1 output(s) for total of 477.470370102000 dcy

stealth address amount amount idx
00: e4eeaa6d222ea1fab816eb8107cb0aa28590489319fe9462640382104578d131 477.470370102000 54857 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": 32923, "vin": [ { "gen": { "height": 32913 } } ], "vout": [ { "amount": 477470370102, "target": { "key": "e4eeaa6d222ea1fab816eb8107cb0aa28590489319fe9462640382104578d131" } } ], "extra": [ 1, 182, 112, 128, 98, 243, 23, 80, 23, 180, 217, 65, 196, 205, 16, 141, 192, 31, 95, 190, 70, 13, 207, 164, 106, 66, 217, 34, 176, 231, 107, 82, 17, 2, 17, 0, 0, 0, 75, 227, 155, 150, 42, 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