Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 533f457cd0e2f3beb7990c47aa47c89baeba4ffa81d483421effe4576ea61317

Tx prefix hash: 17e5dd85dadf15b16bd9f323c439c1b3115137b60543a4eda3f2a77681bef17d
Tx public key: 7bb6c7e63c0412c8f060debc5bbfdc7bda8b40d023763e53ffa3bdfcaa541afd
Timestamp: 1724352493 Timestamp [UCT]: 2024-08-22 18:48:13 Age [y:d:h:m:s]: 00:267:10:25:41
Block: 1093646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191018 RingCT/type: yes/0
Extra: 017bb6c7e63c0412c8f060debc5bbfdc7bda8b40d023763e53ffa3bdfcaa541afd021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b0f28584b2c1570ba63d9149d0feaf26edd9e72932e2ed6dd5b510cd1bae97e 0.600000000000 1568631 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": 1093656, "vin": [ { "gen": { "height": 1093646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b0f28584b2c1570ba63d9149d0feaf26edd9e72932e2ed6dd5b510cd1bae97e" } } ], "extra": [ 1, 123, 182, 199, 230, 60, 4, 18, 200, 240, 96, 222, 188, 91, 191, 220, 123, 218, 139, 64, 208, 35, 118, 62, 83, 255, 163, 189, 252, 170, 84, 26, 253, 2, 17, 0, 0, 0, 6, 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