Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf6f525bb8a768c2d85ee4d4f5620b4f90a8492516a18602ba993ed1ecacda0

Tx prefix hash: 120d0aeddb8b5bf37a5071e38c401431904ee7f17dd2cb31cfda8d71dd11f10c
Tx public key: e56f83ac7593d4cf13684a9b90a36fab5f0df95eecc8e93a32d2743261033f24
Timestamp: 1709704910 Timestamp [UCT]: 2024-03-06 06:01:50 Age [y:d:h:m:s]: 01:063:09:48:42
Block: 972217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306319 RingCT/type: yes/0
Extra: 01e56f83ac7593d4cf13684a9b90a36fab5f0df95eecc8e93a32d2743261033f240211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0867fa00b7b48bb0ce4b659c7bfe11082f6a54349f283463bee912a233fc58d 0.600000000000 1432124 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": 972227, "vin": [ { "gen": { "height": 972217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0867fa00b7b48bb0ce4b659c7bfe11082f6a54349f283463bee912a233fc58d" } } ], "extra": [ 1, 229, 111, 131, 172, 117, 147, 212, 207, 19, 104, 74, 155, 144, 163, 111, 171, 95, 13, 249, 94, 236, 200, 233, 58, 50, 210, 116, 50, 97, 3, 63, 36, 2, 17, 0, 0, 0, 9, 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