Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6b0f5d67cefdc382c055c39c60d979bd2fa54d86af7f53ee4014a3bfbe497b3

Tx prefix hash: f51ac4fb1bfa64b1668654818ceb3813d3ef7a718ba188706c58d68cdf817598
Tx public key: a538e8b645bfc4145e7b018661e4dbfb45ae498940b6410916f2f940d213417d
Timestamp: 1732351010 Timestamp [UCT]: 2024-11-23 08:36:50 Age [y:d:h:m:s]: 00:000:12:59:06
Block: 1159858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377 RingCT/type: yes/0
Extra: 01a538e8b645bfc4145e7b018661e4dbfb45ae498940b6410916f2f940d213417d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d584ccaa1b59346b5a7f4a6e2571cc11a8f332522e67822fc59a29b6503e2f0 0.600000000000 1645497 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": 1159868, "vin": [ { "gen": { "height": 1159858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d584ccaa1b59346b5a7f4a6e2571cc11a8f332522e67822fc59a29b6503e2f0" } } ], "extra": [ 1, 165, 56, 232, 182, 69, 191, 196, 20, 94, 123, 1, 134, 97, 228, 219, 251, 69, 174, 73, 137, 64, 182, 65, 9, 22, 242, 249, 64, 210, 19, 65, 125, 2, 17, 0, 0, 0, 5, 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