Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bd276ca1d7cb772e4e58126d870391274a6c72cd995791c00423d4963ff96cb

Tx prefix hash: 6d356760ac24d045165ad55dbc7d084b9cd0bd621bbeeb199a3e75fa5fd4ea60
Tx public key: 018b09096f3d448bce2dd0396fb9c4b7e1febd9e4b6359080cf7dd3ab564e7ea
Timestamp: 1687014903 Timestamp [UCT]: 2023-06-17 15:15:03 Age [y:d:h:m:s]: 01:276:15:38:57
Block: 784345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458901 RingCT/type: yes/0
Extra: 01018b09096f3d448bce2dd0396fb9c4b7e1febd9e4b6359080cf7dd3ab564e7ea021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.545751123000 dcy

stealth address amount amount idx
00: b047f211ba50252485b82b15ada233dce2ab73c689be98bc9fcd8ca1468faad8 1.545751123000 1234232 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": 784355, "vin": [ { "gen": { "height": 784345 } } ], "vout": [ { "amount": 1545751123, "target": { "key": "b047f211ba50252485b82b15ada233dce2ab73c689be98bc9fcd8ca1468faad8" } } ], "extra": [ 1, 1, 139, 9, 9, 111, 61, 68, 139, 206, 45, 208, 57, 111, 185, 196, 183, 225, 254, 189, 158, 75, 99, 89, 8, 12, 247, 221, 58, 181, 100, 231, 234, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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