Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8ecdeed7e3ce6a22e0ee398ea222bff42cfe2c5ca278ec6f2546d7396ec66c4

Tx prefix hash: c9592e19e47b8af84dc13814f100f95f8b21a0a315572d4b944fe29c6b9de753
Tx public key: 27d12f4681005e584252a7f07ea4e7e4ffdbbd3153a8e316f348f10e704784af
Timestamp: 1763129308 Timestamp [UCT]: 2025-11-14 14:08:28 Age [y:d:h:m:s]: 00:039:01:41:26
Block: 1411997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27957 RingCT/type: yes/0
Extra: 0127d12f4681005e584252a7f07ea4e7e4ffdbbd3153a8e316f348f10e704784af021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0062a1aaf8be0239733496c89000e75e2b66e80fe58a5b3ce16a2f347a5aec33 0.600000000000 1900462 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": 1412007, "vin": [ { "gen": { "height": 1411997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0062a1aaf8be0239733496c89000e75e2b66e80fe58a5b3ce16a2f347a5aec33" } } ], "extra": [ 1, 39, 209, 47, 70, 129, 0, 94, 88, 66, 82, 167, 240, 126, 164, 231, 228, 255, 219, 189, 49, 83, 168, 227, 22, 243, 72, 241, 14, 112, 71, 132, 175, 2, 17, 0, 0, 0, 6, 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