Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f89e119d53a44aef5371e91a1553f212ec2ab4f00668e2fd62fc5d8db0db7679

Tx prefix hash: c55ae9e4b8510c1ed1f63c022bc0bf3dc67f956cc5bd4d44d82865685e3cbb6c
Tx public key: ff239555fc2fd43e714f1cda1d1e38b80e4f47f2a0f10dd0dce9cecce59d9b0b
Timestamp: 1706120345 Timestamp [UCT]: 2024-01-24 18:19:05 Age [y:d:h:m:s]: 01:108:14:59:03
Block: 942458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338750 RingCT/type: yes/0
Extra: 01ff239555fc2fd43e714f1cda1d1e38b80e4f47f2a0f10dd0dce9cecce59d9b0b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8347eb681b5fd694cf32a352b7112305511f753f6860784350a8485b2671e26c 0.600000000000 1400630 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": 942468, "vin": [ { "gen": { "height": 942458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8347eb681b5fd694cf32a352b7112305511f753f6860784350a8485b2671e26c" } } ], "extra": [ 1, 255, 35, 149, 85, 252, 47, 212, 62, 113, 79, 28, 218, 29, 30, 56, 184, 14, 79, 71, 242, 160, 241, 13, 208, 220, 233, 206, 204, 229, 157, 155, 11, 2, 17, 0, 0, 0, 4, 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