Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d35a3bf1a9b8b44ad37d2471f901f3bde585fb50c016d6c92545e23cca2dc83

Tx prefix hash: fff7d257ce6eecb9f8503dafe9c4526e00beb1b5df54f3063da085d29fc66b59
Tx public key: 7ea6a4be81f8420ed2e58b91cebe89575db703bb1ea7e3feda7bd07acf8dfceb
Timestamp: 1759845883 Timestamp [UCT]: 2025-10-07 14:04:43 Age [y:d:h:m:s]: 00:088:09:24:48
Block: 1384787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63297 RingCT/type: yes/0
Extra: 017ea6a4be81f8420ed2e58b91cebe89575db703bb1ea7e3feda7bd07acf8dfceb021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05a6431cc5aa0881082fb5cc89d15865a574072ea5209e9a5b2e0eae2b57311b 0.600000000000 1872944 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": 1384797, "vin": [ { "gen": { "height": 1384787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05a6431cc5aa0881082fb5cc89d15865a574072ea5209e9a5b2e0eae2b57311b" } } ], "extra": [ 1, 126, 166, 164, 190, 129, 248, 66, 14, 210, 229, 139, 145, 206, 190, 137, 87, 93, 183, 3, 187, 30, 167, 227, 254, 218, 123, 208, 122, 207, 141, 252, 235, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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