Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9d0e6f612b1d27450156a4af2d518fa7ab8947b687e3dc41395e9573c84e33c

Tx prefix hash: dd95fcd86c1f6f241f8ace19726289105d31b975a4d22eac1e32d425476a9d60
Tx public key: 13f3f897af879fa6ff99325dc0eedd0754f0a26512f759fe24535e0ee057fa86
Timestamp: 1736498962 Timestamp [UCT]: 2025-01-10 08:49:22 Age [y:d:h:m:s]: 00:159:04:35:49
Block: 1194201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113465 RingCT/type: yes/0
Extra: 0113f3f897af879fa6ff99325dc0eedd0754f0a26512f759fe24535e0ee057fa860211000000151f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 199f3557ba9fafbb3acabf88808339845b463802d2fd8eb2d142b7097b2d28cb 0.600000000000 1680768 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": 1194211, "vin": [ { "gen": { "height": 1194201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "199f3557ba9fafbb3acabf88808339845b463802d2fd8eb2d142b7097b2d28cb" } } ], "extra": [ 1, 19, 243, 248, 151, 175, 135, 159, 166, 255, 153, 50, 93, 192, 238, 221, 7, 84, 240, 162, 101, 18, 247, 89, 254, 36, 83, 94, 14, 224, 87, 250, 134, 2, 17, 0, 0, 0, 21, 31, 10, 83, 235, 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