Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6fb7c9b8f96185108db4b08aa9949c5845f4c6471a375dc78e9326f8941932f

Tx prefix hash: c5c53d95c42d51fb3095cc971570d5c73677f49f0192640859f14bbb8b5de360
Tx public key: 0047578e5d889acf36f783716d7a6c4c78647776622d2ff0a710ec96ffe2c8ff
Timestamp: 1577784318 Timestamp [UCT]: 2019-12-31 09:25:18 Age [y:d:h:m:s]: 05:002:22:46:00
Block: 35570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152173 RingCT/type: yes/0
Extra: 010047578e5d889acf36f783716d7a6c4c78647776622d2ff0a710ec96ffe2c8ff0211000000014943cd9f000000000000000000

1 output(s) for total of 467.888831071000 dcy

stealth address amount amount idx
00: 76c0ca4e6d00dd662f012fce9de07a9938b7b218a77e05499ce384e726fa247f 467.888831071000 60059 of 0

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": 35580, "vin": [ { "gen": { "height": 35570 } } ], "vout": [ { "amount": 467888831071, "target": { "key": "76c0ca4e6d00dd662f012fce9de07a9938b7b218a77e05499ce384e726fa247f" } } ], "extra": [ 1, 0, 71, 87, 142, 93, 136, 154, 207, 54, 247, 131, 113, 109, 122, 108, 76, 120, 100, 119, 118, 98, 45, 47, 240, 167, 16, 236, 150, 255, 226, 200, 255, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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