Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 041e758fe5537581dd314bb0f154ad5af4288e5f62a0e1a5f544bbe6c5c87711

Tx prefix hash: 26ca8b93e4d7cdeb0b042f51593ea19e110736cd0f7ccd6f472641f3b32ae045
Tx public key: 38c92af035393e4cc22d486b1297062dd2cfa0cf921f025a2c7988c89f175902
Timestamp: 1701235162 Timestamp [UCT]: 2023-11-29 05:19:22 Age [y:d:h:m:s]: 01:124:21:50:45
Block: 901984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350417 RingCT/type: yes/0
Extra: 0138c92af035393e4cc22d486b1297062dd2cfa0cf921f025a2c7988c89f1759020211000000024b8f5122000000000000000000

1 output(s) for total of 0.630017419000 dcy

stealth address amount amount idx
00: b407ef9d955297a4c6e892379978e00a1b5e305e7fe5e8f01074a0ce98551d82 0.630017419000 1358585 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": 901994, "vin": [ { "gen": { "height": 901984 } } ], "vout": [ { "amount": 630017419, "target": { "key": "b407ef9d955297a4c6e892379978e00a1b5e305e7fe5e8f01074a0ce98551d82" } } ], "extra": [ 1, 56, 201, 42, 240, 53, 57, 62, 76, 194, 45, 72, 107, 18, 151, 6, 45, 210, 207, 160, 207, 146, 31, 2, 90, 44, 121, 136, 200, 159, 23, 89, 2, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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