Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd765b5344b972f2bd4ae37849911d17ad693617d99d8b05269889c14880e60

Tx prefix hash: 891f0230c791a821f96574649bcac284763f9c5f4b8b091a58a0ee6ce2d0fcd2
Tx public key: addb864c9335489afa6f80dafb83df1e5c55a02d771ed8d5a3bdff7ca57add17
Timestamp: 1726486786 Timestamp [UCT]: 2024-09-16 11:39:46 Age [y:d:h:m:s]: 00:201:10:37:55
Block: 1111336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143787 RingCT/type: yes/0
Extra: 01addb864c9335489afa6f80dafb83df1e5c55a02d771ed8d5a3bdff7ca57add17021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f111b0bfb4af8ec5d2e788fd43ed2997f7587c1020b520ca59c0b57a6632aeac 0.600000000000 1590259 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": 1111346, "vin": [ { "gen": { "height": 1111336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f111b0bfb4af8ec5d2e788fd43ed2997f7587c1020b520ca59c0b57a6632aeac" } } ], "extra": [ 1, 173, 219, 134, 76, 147, 53, 72, 154, 250, 111, 128, 218, 251, 131, 223, 30, 92, 85, 160, 45, 119, 30, 216, 213, 163, 189, 255, 124, 165, 122, 221, 23, 2, 17, 0, 0, 0, 9, 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