Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2eb29de2d125d4668fa8959bf5df6ddb2c7c725ce2b30914d8074746bd5a260

Tx prefix hash: 6e2a17e441cf0021581ff8094c34432ca8dfd86997537417dccab4cab85ff021
Tx public key: 6827bbd080a0805e6c38b5dc7540f0cfb445b8fcc0065e1a43a9e03c506d0a72
Timestamp: 1577722014 Timestamp [UCT]: 2019-12-30 16:06:54 Age [y:d:h:m:s]: 05:071:21:29:46
Block: 35149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201146 RingCT/type: yes/0
Extra: 016827bbd080a0805e6c38b5dc7540f0cfb445b8fcc0065e1a43a9e03c506d0a72021100000001d81c26c0000000000000000000

1 output(s) for total of 469.394100237000 dcy

stealth address amount amount idx
00: a09420dc3a5a93291a509c1e36f774d2bc343b072d5b9c75e88a8b08311120af 469.394100237000 59198 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": 35159, "vin": [ { "gen": { "height": 35149 } } ], "vout": [ { "amount": 469394100237, "target": { "key": "a09420dc3a5a93291a509c1e36f774d2bc343b072d5b9c75e88a8b08311120af" } } ], "extra": [ 1, 104, 39, 187, 208, 128, 160, 128, 94, 108, 56, 181, 220, 117, 64, 240, 207, 180, 69, 184, 252, 192, 6, 94, 26, 67, 169, 224, 60, 80, 109, 10, 114, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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