Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0667cd70b6bda2103c72048a4a76c9fc4ec3fea0557f32233ea0b6a6135a541

Tx prefix hash: 4a89c0c236b5478df6d34f7aecccced5fcf221480be13bde2e31bc3adbdb6454
Tx public key: 47c4bbe9d0dd0203db5005c565ba503963f65fbecfa224de59cc6dc22fb2cfac
Timestamp: 1699885172 Timestamp [UCT]: 2023-11-13 14:19:32 Age [y:d:h:m:s]: 01:148:14:02:07
Block: 890795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367381 RingCT/type: yes/0
Extra: 0147c4bbe9d0dd0203db5005c565ba503963f65fbecfa224de59cc6dc22fb2cfac021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.686161545000 dcy

stealth address amount amount idx
00: 07fa1adb12ab373fab8058e191b64425bd3a2eac15ad8a481f75ab2ae342ed85 0.686161545000 1346826 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": 890805, "vin": [ { "gen": { "height": 890795 } } ], "vout": [ { "amount": 686161545, "target": { "key": "07fa1adb12ab373fab8058e191b64425bd3a2eac15ad8a481f75ab2ae342ed85" } } ], "extra": [ 1, 71, 196, 187, 233, 208, 221, 2, 3, 219, 80, 5, 197, 101, 186, 80, 57, 99, 246, 95, 190, 207, 162, 36, 222, 89, 204, 109, 194, 47, 178, 207, 172, 2, 17, 0, 0, 0, 1, 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