Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c03d4afc6a9762f067756b7daed8be9a5671f1001c1164c352e69d645b721f63

Tx prefix hash: 1aeb8ed03ac835e5542132fe8f7eb84e157e89dcd3ec65bc0e397766c6ebd789
Tx public key: 05346d25e9b4a36ada4dcece0e8d6b7a7d933066dc5b19600439fd66fedac0b1
Timestamp: 1704619095 Timestamp [UCT]: 2024-01-07 09:18:15 Age [y:d:h:m:s]: 00:313:01:23:44
Block: 930022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224173 RingCT/type: yes/0
Extra: 0105346d25e9b4a36ada4dcece0e8d6b7a7d933066dc5b19600439fd66fedac0b102110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49e5fb8cc857136965242770b2c5f5c0c208fa43c868db83a488c6745d17bde9 0.600000000000 1387900 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": 930032, "vin": [ { "gen": { "height": 930022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49e5fb8cc857136965242770b2c5f5c0c208fa43c868db83a488c6745d17bde9" } } ], "extra": [ 1, 5, 52, 109, 37, 233, 180, 163, 106, 218, 77, 206, 206, 14, 141, 107, 122, 125, 147, 48, 102, 220, 91, 25, 96, 4, 57, 253, 102, 254, 218, 192, 177, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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