Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8b7a50980f8ff673230aac74c0e892a6140ff6cb9c945a5c68490ae1f201d79

Tx prefix hash: b87f4a73bc18f215bb38baec7e19d9c6b5cc2ea9da7e9cb48a5b5a4a14ec5b29
Tx public key: 6d7ce4a94c30287cf111408e5565dcab8d50f4cafb8601d58b7fd69ed6783fb8
Timestamp: 1723486246 Timestamp [UCT]: 2024-08-12 18:10:46 Age [y:d:h:m:s]: 00:216:18:11:27
Block: 1086455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154810 RingCT/type: yes/0
Extra: 016d7ce4a94c30287cf111408e5565dcab8d50f4cafb8601d58b7fd69ed6783fb8021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e15befa90ca53f3fcba97c0565f42819ad2b7b192fd26b79d5a0be5d3c66aecb 0.600000000000 1561052 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": 1086465, "vin": [ { "gen": { "height": 1086455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e15befa90ca53f3fcba97c0565f42819ad2b7b192fd26b79d5a0be5d3c66aecb" } } ], "extra": [ 1, 109, 124, 228, 169, 76, 48, 40, 124, 241, 17, 64, 142, 85, 101, 220, 171, 141, 80, 244, 202, 251, 134, 1, 213, 139, 127, 214, 158, 214, 120, 63, 184, 2, 17, 0, 0, 0, 1, 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