Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8508e368a48d37da4e64da3daab5949e6a6b98ec489764e0483e46b02180ade7

Tx prefix hash: 00953dd7f0b513fd363a726cfe0c8eb9ee2c80cb4d42fd9841fbdfc981dd765d
Tx public key: 6ba678455907dc552f0566ad2af3893949c9768cfbedb983c8e843fcad13f181
Timestamp: 1582402261 Timestamp [UCT]: 2020-02-22 20:11:01 Age [y:d:h:m:s]: 04:309:01:00:00
Block: 70419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113417 RingCT/type: yes/0
Extra: 016ba678455907dc552f0566ad2af3893949c9768cfbedb983c8e843fcad13f18102110000002e8a2ee0d9000000000000000000

1 output(s) for total of 358.652137710000 dcy

stealth address amount amount idx
00: 44e16ef2dc732188dc82410e2a7c59067aceaa150c89e6fd345eb7e40fc1588c 358.652137710000 130114 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": 70429, "vin": [ { "gen": { "height": 70419 } } ], "vout": [ { "amount": 358652137710, "target": { "key": "44e16ef2dc732188dc82410e2a7c59067aceaa150c89e6fd345eb7e40fc1588c" } } ], "extra": [ 1, 107, 166, 120, 69, 89, 7, 220, 85, 47, 5, 102, 173, 42, 243, 137, 57, 73, 201, 118, 140, 251, 237, 185, 131, 200, 232, 67, 252, 173, 19, 241, 129, 2, 17, 0, 0, 0, 46, 138, 46, 224, 217, 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