Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 314baaab0648f649b5f64aebaaac9d454ccbea0a92b116fdd23059c111746fcb

Tx prefix hash: 0ac042b05e9819fca83101aef716a0c8cb32556aced418ff0e98fb321c50f402
Tx public key: a96952e8c66907a2a1fde64ea710888c7b405055f7c271b7ea9eb130a3b3837a
Timestamp: 1738418601 Timestamp [UCT]: 2025-02-01 14:03:21 Age [y:d:h:m:s]: 00:338:08:05:44
Block: 1209828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239654 RingCT/type: yes/0
Extra: 01a96952e8c66907a2a1fde64ea710888c7b405055f7c271b7ea9eb130a3b3837a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e36641de7d4eba2771512133d0b1f25094ccb6ad441ffef2c93bb4926fc20354 0.600000000000 1696575 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": 1209838, "vin": [ { "gen": { "height": 1209828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e36641de7d4eba2771512133d0b1f25094ccb6ad441ffef2c93bb4926fc20354" } } ], "extra": [ 1, 169, 105, 82, 232, 198, 105, 7, 162, 161, 253, 230, 78, 167, 16, 136, 140, 123, 64, 80, 85, 247, 194, 113, 183, 234, 158, 177, 48, 163, 179, 131, 122, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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