Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3842e93244819014f00ae0a084134c4ef9dbc605de6cc0cd5cdf04f8369107e5

Tx prefix hash: 00f87fae39bcdb7d99034ecfbf9c4a59e25fa9eae6f170e0e8e3d797252a9247
Tx public key: 69a21b702df89f56733a4747ca1f5cd0215bd5d0fb91e591f356fe70f1bec3b7
Timestamp: 1759449911 Timestamp [UCT]: 2025-10-03 00:05:11 Age [y:d:h:m:s]: 00:120:03:03:48
Block: 1381487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85845 RingCT/type: yes/0
Extra: 0169a21b702df89f56733a4747ca1f5cd0215bd5d0fb91e591f356fe70f1bec3b7021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7be45225a8b647c3f9a2eebcce5f0135e745c8a9c9354f10773d0f0527d46ed4 0.600000000000 1869606 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": 1381497, "vin": [ { "gen": { "height": 1381487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7be45225a8b647c3f9a2eebcce5f0135e745c8a9c9354f10773d0f0527d46ed4" } } ], "extra": [ 1, 105, 162, 27, 112, 45, 248, 159, 86, 115, 58, 71, 71, 202, 31, 92, 208, 33, 91, 213, 208, 251, 145, 229, 145, 243, 86, 254, 112, 241, 190, 195, 183, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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