Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08262a458cb7e399a5e01406309769262d3d8ef9d918b8af0ebd3d366291db5c

Tx prefix hash: 363d632e643ad2909df36fd7ab4064a5467f100a5515e7a91be188659210b560
Tx public key: 54c37ae79832c5198d208c16c37809b8342448e2d9ab65b27f40e2dcbd503a8f
Timestamp: 1703978964 Timestamp [UCT]: 2023-12-30 23:29:24 Age [y:d:h:m:s]: 01:313:09:16:38
Block: 924725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482815 RingCT/type: yes/0
Extra: 0154c37ae79832c5198d208c16c37809b8342448e2d9ab65b27f40e2dcbd503a8f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e44fc8334c99eb399498398f0a0b09bebfb40c883a7c47c0877ba2d3fd91a751 0.600000000000 1382481 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": 924735, "vin": [ { "gen": { "height": 924725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e44fc8334c99eb399498398f0a0b09bebfb40c883a7c47c0877ba2d3fd91a751" } } ], "extra": [ 1, 84, 195, 122, 231, 152, 50, 197, 25, 141, 32, 140, 22, 195, 120, 9, 184, 52, 36, 72, 226, 217, 171, 101, 178, 127, 64, 226, 220, 189, 80, 58, 143, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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