Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 844303eaf77fd5c4acbb58f7093106808745f014560d9a415f829b31184d3252

Tx prefix hash: be7539c9729487ffce328f8e72775151e5d65e173a621579b3007433f67d50c2
Tx public key: b20ed80df9c1aeb2669e59f03eed3dc1bf062f5a376d5cbda06b8b82d578397e
Timestamp: 1733108766 Timestamp [UCT]: 2024-12-02 03:06:06 Age [y:d:h:m:s]: 00:117:03:10:07
Block: 1166135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83509 RingCT/type: yes/0
Extra: 01b20ed80df9c1aeb2669e59f03eed3dc1bf062f5a376d5cbda06b8b82d578397e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96716fe934d61eb5bf0cde716c3e2987ec07a8068d81bb216cc1c1ba6527cfea 0.600000000000 1651812 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": 1166145, "vin": [ { "gen": { "height": 1166135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96716fe934d61eb5bf0cde716c3e2987ec07a8068d81bb216cc1c1ba6527cfea" } } ], "extra": [ 1, 178, 14, 216, 13, 249, 193, 174, 178, 102, 158, 89, 240, 62, 237, 61, 193, 191, 6, 47, 90, 55, 109, 92, 189, 160, 107, 139, 130, 213, 120, 57, 126, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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