Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e425f5a649ef209b72941b929a84423bff931812eeef5224faa7d49165ad5d9c

Tx prefix hash: e7da6418781c65d652ca34145167436c4efbeda87709ae8700e528e9b95a9a4b
Tx public key: 2f63908dd4ce5a8ff31371e88947e647b7caf38d4074ce3db3eb4a7cd96f8afb
Timestamp: 1581213496 Timestamp [UCT]: 2020-02-09 01:58:16 Age [y:d:h:m:s]: 04:335:11:01:15
Block: 60976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131918 RingCT/type: yes/0
Extra: 012f63908dd4ce5a8ff31371e88947e647b7caf38d4074ce3db3eb4a7cd96f8afb02110000000b4943cd9f000000000000000000

1 output(s) for total of 385.444645163000 dcy

stealth address amount amount idx
00: b2d70e2c23fad7f0168d0b9c8e7c07d605d3ffc57d7d2c94001dd097056e1b13 385.444645163000 112403 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": 60986, "vin": [ { "gen": { "height": 60976 } } ], "vout": [ { "amount": 385444645163, "target": { "key": "b2d70e2c23fad7f0168d0b9c8e7c07d605d3ffc57d7d2c94001dd097056e1b13" } } ], "extra": [ 1, 47, 99, 144, 141, 212, 206, 90, 143, 243, 19, 113, 232, 137, 71, 230, 71, 183, 202, 243, 141, 64, 116, 206, 61, 179, 235, 74, 124, 217, 111, 138, 251, 2, 17, 0, 0, 0, 11, 73, 67, 205, 159, 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