Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e226d362db825b8fa7087f5deed3efc1f6a6d978144b21eb71f20c66cc2534de

Tx prefix hash: 0385f4796c11555db7e82a908b0cf90187d11d95f3a76ae7a619768e31b2f0ba
Tx public key: dd23135211edee4f25eeecf883879961eab9dcae92b0811b384f51020c8d8850
Timestamp: 1714386541 Timestamp [UCT]: 2024-04-29 10:29:01 Age [y:d:h:m:s]: 00:343:20:07:04
Block: 1011016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245779 RingCT/type: yes/0
Extra: 01dd23135211edee4f25eeecf883879961eab9dcae92b0811b384f51020c8d88500211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e97b4e9c4b39ed209c43d8d6ab0fcee691a9265bee40bf8f53b3c120f8b7b52 0.600000000000 1473130 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": 1011026, "vin": [ { "gen": { "height": 1011016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e97b4e9c4b39ed209c43d8d6ab0fcee691a9265bee40bf8f53b3c120f8b7b52" } } ], "extra": [ 1, 221, 35, 19, 82, 17, 237, 238, 79, 37, 238, 236, 248, 131, 135, 153, 97, 234, 185, 220, 174, 146, 176, 129, 27, 56, 79, 81, 2, 12, 141, 136, 80, 2, 17, 0, 0, 0, 3, 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