Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e818ab5fa2c79e1daba018bf75e2f46be1c1ebcf1f88c12b560e2ee6abc8054

Tx prefix hash: d766190bff1a2f9f17c803530681172b6f03ec581fcf8cf695b873343b66f903
Tx public key: f6c68b2be7a51fd0819c464368f62a93cbed8a925b0c873a1668cf1c91f74495
Timestamp: 1727590929 Timestamp [UCT]: 2024-09-29 06:22:09 Age [y:d:h:m:s]: 00:056:22:36:33
Block: 1120495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40675 RingCT/type: yes/0
Extra: 01f6c68b2be7a51fd0819c464368f62a93cbed8a925b0c873a1668cf1c91f74495021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 875b3853d6e2f36bc51dd912cd1cb026dcf2ddefb574bb6d88d76217ace12768 0.600000000000 1602430 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": 1120505, "vin": [ { "gen": { "height": 1120495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875b3853d6e2f36bc51dd912cd1cb026dcf2ddefb574bb6d88d76217ace12768" } } ], "extra": [ 1, 246, 198, 139, 43, 231, 165, 31, 208, 129, 156, 70, 67, 104, 246, 42, 147, 203, 237, 138, 146, 91, 12, 135, 58, 22, 104, 207, 28, 145, 247, 68, 149, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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