Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7297d26256af8e234eef4a033593c5898c4d36e4a26895224cd4a5647edb2f44

Tx prefix hash: d2988080695be189a5896157f49db8d3c875ed46de4f04dacc010a6e374838c8
Tx public key: 6bd3e0c15a022d24ad7ffd7e9b680b2b64158937ca432239a6fd2d612309dd38
Timestamp: 1710654449 Timestamp [UCT]: 2024-03-17 05:47:29 Age [y:d:h:m:s]: 01:238:18:56:21
Block: 980100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429346 RingCT/type: yes/0
Extra: 016bd3e0c15a022d24ad7ffd7e9b680b2b64158937ca432239a6fd2d612309dd380211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770a072a41249bbf16fbef816f47c6ad6d633466c2f4fada918354f8cc7b1715 0.600000000000 1440159 of 15

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": 980110, "vin": [ { "gen": { "height": 980100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770a072a41249bbf16fbef816f47c6ad6d633466c2f4fada918354f8cc7b1715" } } ], "extra": [ 1, 107, 211, 224, 193, 90, 2, 45, 36, 173, 127, 253, 126, 155, 104, 11, 43, 100, 21, 137, 55, 202, 67, 34, 57, 166, 253, 45, 97, 35, 9, 221, 56, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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