Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92e7d5e76ce5147d95e13347025a8ee5cea1668a9a0b7397f56323716b768c79

Tx prefix hash: 5545e9aea2c28c7ea737225509c7a77105386e71a86703f005649688d0f0a9f9
Tx public key: bc4b187ad0f7e6004efb6e6dbca488279e89b5ef0add3d8502894c00170e3d5a
Timestamp: 1727963359 Timestamp [UCT]: 2024-10-03 13:49:19 Age [y:d:h:m:s]: 01:037:05:25:08
Block: 1123583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284985 RingCT/type: yes/0
Extra: 01bc4b187ad0f7e6004efb6e6dbca488279e89b5ef0add3d8502894c00170e3d5a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bfd9dd4fdb914a3387c646a872343e01027e9bb7c3bc968381adb487d076a47 0.600000000000 1606118 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": 1123593, "vin": [ { "gen": { "height": 1123583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bfd9dd4fdb914a3387c646a872343e01027e9bb7c3bc968381adb487d076a47" } } ], "extra": [ 1, 188, 75, 24, 122, 208, 247, 230, 0, 78, 251, 110, 109, 188, 164, 136, 39, 158, 137, 181, 239, 10, 221, 61, 133, 2, 137, 76, 0, 23, 14, 61, 90, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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