Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 059a74165fdad0f78f073cb7a0186aab847b8664ab4dda2592f8ff661b7bd026

Tx prefix hash: 38d50960718ab08e17c97ba8294b9ab238f02525a8837face057ab18aa3103ed
Tx public key: 1c29e87c6b07fd78d41e9a780673bc9a92a5ca756de17ea6b6d478765311cb1e
Timestamp: 1728912925 Timestamp [UCT]: 2024-10-14 13:35:25 Age [y:d:h:m:s]: 00:041:00:30:49
Block: 1131455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29282 RingCT/type: yes/0
Extra: 011c29e87c6b07fd78d41e9a780673bc9a92a5ca756de17ea6b6d478765311cb1e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1744ddb9bae87106ef9c0f1762195a758b674dc977cf00bdaa873d9ca8f39c29 0.600000000000 1614358 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": 1131465, "vin": [ { "gen": { "height": 1131455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1744ddb9bae87106ef9c0f1762195a758b674dc977cf00bdaa873d9ca8f39c29" } } ], "extra": [ 1, 28, 41, 232, 124, 107, 7, 253, 120, 212, 30, 154, 120, 6, 115, 188, 154, 146, 165, 202, 117, 109, 225, 126, 166, 182, 212, 120, 118, 83, 17, 203, 30, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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