Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e58d538e1cf6e051cc782bf49f65579ecab51fc2941a9df4e64cf831a13aa1aa

Tx prefix hash: 05fd69bff8a74c3961de61842aa4937c60f0893ba9824e645ceb9727783bca09
Tx public key: 1f6dd8971e5cf6e9de82ffc0ad7fae0d0f6e234e66c760235604feb7a8f417d5
Timestamp: 1732491038 Timestamp [UCT]: 2024-11-24 23:30:38 Age [y:d:h:m:s]: 00:109:07:41:00
Block: 1161018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77937 RingCT/type: yes/0
Extra: 011f6dd8971e5cf6e9de82ffc0ad7fae0d0f6e234e66c760235604feb7a8f417d50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b185483a5eae576c5b412f0fca2ec9dfddd295d50f90e4ca98477c1fbca84db5 0.600000000000 1646669 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": 1161028, "vin": [ { "gen": { "height": 1161018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b185483a5eae576c5b412f0fca2ec9dfddd295d50f90e4ca98477c1fbca84db5" } } ], "extra": [ 1, 31, 109, 216, 151, 30, 92, 246, 233, 222, 130, 255, 192, 173, 127, 174, 13, 15, 110, 35, 78, 102, 199, 96, 35, 86, 4, 254, 183, 168, 244, 23, 213, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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