Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f5aa655d3b4de4ce9a89aa5cc52c18af98009e197134556ecb2f96277e032ac

Tx prefix hash: 65eed777723a417b7fdcff8bbcb344770dd5114277fe74b77c92fcd2f5441fb5
Tx public key: f6d694aab1b2c0f90ae7fdc98db6ea3d0464233b1ad68025c8a4b497f208dcc1
Timestamp: 1736682972 Timestamp [UCT]: 2025-01-12 11:56:12 Age [y:d:h:m:s]: 00:157:08:29:17
Block: 1195723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112161 RingCT/type: yes/0
Extra: 01f6d694aab1b2c0f90ae7fdc98db6ea3d0464233b1ad68025c8a4b497f208dcc10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08eed4f28c654b047b84ac77efb0462a23b321650f7257fffe9af790a660f32c 0.600000000000 1682316 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": 1195733, "vin": [ { "gen": { "height": 1195723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08eed4f28c654b047b84ac77efb0462a23b321650f7257fffe9af790a660f32c" } } ], "extra": [ 1, 246, 214, 148, 170, 177, 178, 192, 249, 10, 231, 253, 201, 141, 182, 234, 61, 4, 100, 35, 59, 26, 214, 128, 37, 200, 164, 180, 151, 242, 8, 220, 193, 2, 17, 0, 0, 0, 1, 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