Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8084f30b70b48d4bfa5d539d4f44738184b7a2a9084d1d75fc1669b664318b6

Tx prefix hash: bbe41ea2a8d77fbcfc0a92129fd89a1ef659bad996cd15940e250d8900c63be7
Tx public key: db6410cb5e476098ab2f8893a6f64b1b9cdb0d8cacdec5616d91a10ff931cc64
Timestamp: 1725026418 Timestamp [UCT]: 2024-08-30 14:00:18 Age [y:d:h:m:s]: 00:116:11:25:22
Block: 1099218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83332 RingCT/type: yes/0
Extra: 01db6410cb5e476098ab2f8893a6f64b1b9cdb0d8cacdec5616d91a10ff931cc64021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c38a2dfe793959c967faf598ab1bf2f0f947677b6bcdaaf3fae88b274319971 0.600000000000 1575159 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": 1099228, "vin": [ { "gen": { "height": 1099218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c38a2dfe793959c967faf598ab1bf2f0f947677b6bcdaaf3fae88b274319971" } } ], "extra": [ 1, 219, 100, 16, 203, 94, 71, 96, 152, 171, 47, 136, 147, 166, 246, 75, 27, 156, 219, 13, 140, 172, 222, 197, 97, 109, 145, 161, 15, 249, 49, 204, 100, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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