Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5868a5008cf45dee59bb9466c42f75479c877d9d7f0c72a2d942ff71753200d5

Tx prefix hash: 843ef63f60bb1830548e18ed76b8d12247bf75f89249a3dc695edf89a28a2a09
Tx public key: 964e0ee5e73276bf91c6de51f8f149c81fbdd00f9e80b40af74b07a0e4412e53
Timestamp: 1709388473 Timestamp [UCT]: 2024-03-02 14:07:53 Age [y:d:h:m:s]: 01:100:04:50:02
Block: 969587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332663 RingCT/type: yes/0
Extra: 01964e0ee5e73276bf91c6de51f8f149c81fbdd00f9e80b40af74b07a0e4412e5302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b9a2bf38602acb5968a9cae985a704585edb88e82a0c756012916f9ea761940 0.600000000000 1429424 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": 969597, "vin": [ { "gen": { "height": 969587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b9a2bf38602acb5968a9cae985a704585edb88e82a0c756012916f9ea761940" } } ], "extra": [ 1, 150, 78, 14, 229, 231, 50, 118, 191, 145, 198, 222, 81, 248, 241, 73, 200, 31, 189, 208, 15, 158, 128, 180, 10, 247, 75, 7, 160, 228, 65, 46, 83, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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