Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ee107011f552e2b07987086e4cc2516951f5a251993bba5e4827b8b85268e48

Tx prefix hash: 602c2b17a7930347ba9605782194f05a2148aed733fd11c67160e712c431625f
Tx public key: ef58246f69c797bb3aeadb01df17272be8d544fb41011da0b7b9c768dfc10688
Timestamp: 1577719978 Timestamp [UCT]: 2019-12-30 15:32:58 Age [y:d:h:m:s]: 04:334:23:11:10
Block: 35128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128497 RingCT/type: yes/0
Extra: 01ef58246f69c797bb3aeadb01df17272be8d544fb41011da0b7b9c768dfc10688021100000002feadaf7f000000000000000000

1 output(s) for total of 469.469311597000 dcy

stealth address amount amount idx
00: 003dc6d91d8f6bafa229ea67daab13960b7ea7d1ffad8aa0a881ac0028dbf85b 469.469311597000 59169 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": 35138, "vin": [ { "gen": { "height": 35128 } } ], "vout": [ { "amount": 469469311597, "target": { "key": "003dc6d91d8f6bafa229ea67daab13960b7ea7d1ffad8aa0a881ac0028dbf85b" } } ], "extra": [ 1, 239, 88, 36, 111, 105, 199, 151, 187, 58, 234, 219, 1, 223, 23, 39, 43, 232, 213, 68, 251, 65, 1, 29, 160, 183, 185, 199, 104, 223, 193, 6, 136, 2, 17, 0, 0, 0, 2, 254, 173, 175, 127, 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