Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a5a4f7142ad6917ad4ceb0d5e67405a52d3aff8ab92a333f457e91934c40e2f

Tx prefix hash: 748c33183fa2e25a3bcde15c6f72e4c960f3a620bdaf0251705b0f81abf7c736
Tx public key: 53054ce9e381d8dd99846d074570123bb7f7ec5cb3b0ce77f86dc65f8cb60de8
Timestamp: 1583977819 Timestamp [UCT]: 2020-03-12 01:50:19 Age [y:d:h:m:s]: 04:251:20:41:30
Block: 80870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075113 RingCT/type: yes/0
Extra: 0153054ce9e381d8dd99846d074570123bb7f7ec5cb3b0ce77f86dc65f8cb60de80211000000014ac5aa02000000000000000000

1 output(s) for total of 331.165363651000 dcy

stealth address amount amount idx
00: 906987c017c6caa7f3e2dd06d0bdcdd24dcce9ca70dc73834dd01d992771e9a8 331.165363651000 147936 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": 80880, "vin": [ { "gen": { "height": 80870 } } ], "vout": [ { "amount": 331165363651, "target": { "key": "906987c017c6caa7f3e2dd06d0bdcdd24dcce9ca70dc73834dd01d992771e9a8" } } ], "extra": [ 1, 83, 5, 76, 233, 227, 129, 216, 221, 153, 132, 109, 7, 69, 112, 18, 59, 183, 247, 236, 92, 179, 176, 206, 119, 248, 109, 198, 95, 140, 182, 13, 232, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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