Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6abbd10fc405fa73bfd6a6009e1264a9009889e28e8eb208d45a1912aa0081ef

Tx prefix hash: 957d83ef2b6d61eefcb3e89908aaa21396073deca187b183375bcf5c30705562
Tx public key: 09b4b5068b00486c9bbbb12329c4ae64c31f12510ee38ae4ee90f8f7ed310702
Timestamp: 1581971486 Timestamp [UCT]: 2020-02-17 20:31:26 Age [y:d:h:m:s]: 04:315:09:58:30
Block: 67029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117802 RingCT/type: yes/0
Extra: 0109b4b5068b00486c9bbbb12329c4ae64c31f12510ee38ae4ee90f8f7ed3107020211000000184ac5aa02000000000000000000

1 output(s) for total of 368.049223640000 dcy

stealth address amount amount idx
00: f7c121041207b3fbfefd24e956ab12d69307ccc960000857655a2b9d7e5eee0e 368.049223640000 123449 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": 67039, "vin": [ { "gen": { "height": 67029 } } ], "vout": [ { "amount": 368049223640, "target": { "key": "f7c121041207b3fbfefd24e956ab12d69307ccc960000857655a2b9d7e5eee0e" } } ], "extra": [ 1, 9, 180, 181, 6, 139, 0, 72, 108, 155, 187, 177, 35, 41, 196, 174, 100, 195, 31, 18, 81, 14, 227, 138, 228, 238, 144, 248, 247, 237, 49, 7, 2, 2, 17, 0, 0, 0, 24, 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