Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 088f47581d9d058527a52911e5a074412e1c17748f414a14853f407f565d6af6

Tx prefix hash: 7fdc446fd6eaa03cde457b2117dc0f3af4830df8cbc0fdbfc1ae16aac0ca97e4
Tx public key: 54c6f3b58f1c545705ce8aa46574cad565c753697095a24147ac1a86f7989830
Timestamp: 1763966428 Timestamp [UCT]: 2025-11-24 06:40:28 Age [y:d:h:m:s]: 00:003:10:47:58
Block: 1418925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2487 RingCT/type: yes/0
Extra: 0154c6f3b58f1c545705ce8aa46574cad565c753697095a24147ac1a86f7989830021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2eebb8cb3b2ff361f3c8774f8dc4eb6db8bee59790eebe3dfccc139b70c8de2 0.600000000000 1907458 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": 1418935, "vin": [ { "gen": { "height": 1418925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2eebb8cb3b2ff361f3c8774f8dc4eb6db8bee59790eebe3dfccc139b70c8de2" } } ], "extra": [ 1, 84, 198, 243, 181, 143, 28, 84, 87, 5, 206, 138, 164, 101, 116, 202, 213, 101, 199, 83, 105, 112, 149, 162, 65, 71, 172, 26, 134, 247, 152, 152, 48, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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