Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d3241d6eafc49d124248383e18800b60dd069c85cbf9c4e863202db75940db

Tx prefix hash: 78b06ea62d1d1d75000c6345a8b2346c6c174bc2bd5dce4ab56a2f5dc10daad8
Tx public key: b10f00de098dbc194d5ecd30de1ca45d55c4c47df00dba9f25fd2c64edfe3f75
Timestamp: 1712994078 Timestamp [UCT]: 2024-04-13 07:41:18 Age [y:d:h:m:s]: 00:317:15:57:03
Block: 999458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227090 RingCT/type: yes/0
Extra: 01b10f00de098dbc194d5ecd30de1ca45d55c4c47df00dba9f25fd2c64edfe3f7502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76cfc6dd9658ac323035285f84632430073df2458c7217521f5442e229e9b294 0.600000000000 1459938 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": 999468, "vin": [ { "gen": { "height": 999458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76cfc6dd9658ac323035285f84632430073df2458c7217521f5442e229e9b294" } } ], "extra": [ 1, 177, 15, 0, 222, 9, 141, 188, 25, 77, 94, 205, 48, 222, 28, 164, 93, 85, 196, 196, 125, 240, 13, 186, 159, 37, 253, 44, 100, 237, 254, 63, 117, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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