Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f49beb4421985fd85c530d588c504f3d084a7b1975fcbc7bd57e7bb2af12ee6

Tx prefix hash: a09455f95bee869961952be468bdf079a2bc8accdaf7037d7e86ed8a4092af34
Tx public key: dd0801baff7ecf6c552b8d80cfe1179d3185e6096769a7c3d3630e6ef8805aed
Timestamp: 1736020011 Timestamp [UCT]: 2025-01-04 19:46:51 Age [y:d:h:m:s]: 00:164:22:49:52
Block: 1190234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117593 RingCT/type: yes/0
Extra: 01dd0801baff7ecf6c552b8d80cfe1179d3185e6096769a7c3d3630e6ef8805aed021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31b6780c88229fd782d8bd2fd2f67be9e1b492ed4b96aa5add0570a54b07ca0a 0.600000000000 1676749 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": 1190244, "vin": [ { "gen": { "height": 1190234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31b6780c88229fd782d8bd2fd2f67be9e1b492ed4b96aa5add0570a54b07ca0a" } } ], "extra": [ 1, 221, 8, 1, 186, 255, 126, 207, 108, 85, 43, 141, 128, 207, 225, 23, 157, 49, 133, 230, 9, 103, 105, 167, 195, 211, 99, 14, 110, 248, 128, 90, 237, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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