Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f7d34af28e3af9e9e92125de96d7268ca4fcd748d34d74868ab8ff2e92ff78

Tx prefix hash: a1334f0bfcf2a1de47e6a8928c2408729b0f116b7ba56ee942a625114b03a3d6
Tx public key: b255b7ed50c94948dbf9b5cb8f9b041818afedbd88c103964ae98bfb8d77591a
Timestamp: 1741103509 Timestamp [UCT]: 2025-03-04 15:51:49 Age [y:d:h:m:s]: 00:262:00:03:27
Block: 1232055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184988 RingCT/type: yes/0
Extra: 01b255b7ed50c94948dbf9b5cb8f9b041818afedbd88c103964ae98bfb8d77591a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2789efff794484e74a3cc6566d7a0f9e5b9a33e4e4efa87fa1c3ffd17e1bad0a 0.600000000000 1718966 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": 1232065, "vin": [ { "gen": { "height": 1232055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2789efff794484e74a3cc6566d7a0f9e5b9a33e4e4efa87fa1c3ffd17e1bad0a" } } ], "extra": [ 1, 178, 85, 183, 237, 80, 201, 73, 72, 219, 249, 181, 203, 143, 155, 4, 24, 24, 175, 237, 189, 136, 193, 3, 150, 74, 233, 139, 251, 141, 119, 89, 26, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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