Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eda6b5500cc9a52cabe977f0ab783cff38aa7f994f78443b3a5c7100f120a2f

Tx prefix hash: 36b532ae20d77a1f749118b46a5a478a85ba57ac797589c0a56038743a23d47d
Tx public key: 77c9e519f85dfb10e9b9071f82745504b4f6297f15d83828b5d74478345e0458
Timestamp: 1751203755 Timestamp [UCT]: 2025-06-29 13:29:15 Age [y:d:h:m:s]: 00:140:03:07:55
Block: 1315219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98276 RingCT/type: yes/0
Extra: 0177c9e519f85dfb10e9b9071f82745504b4f6297f15d83828b5d74478345e0458021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8197b6065f1647913bc8c72120fa22cc9aa6ee48b5f35b26f5077b37f43d4c3e 0.600000000000 1802872 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": 1315229, "vin": [ { "gen": { "height": 1315219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8197b6065f1647913bc8c72120fa22cc9aa6ee48b5f35b26f5077b37f43d4c3e" } } ], "extra": [ 1, 119, 201, 229, 25, 248, 93, 251, 16, 233, 185, 7, 31, 130, 116, 85, 4, 180, 246, 41, 127, 21, 216, 56, 40, 181, 215, 68, 120, 52, 94, 4, 88, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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