Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1a535f10a93d4a13f55669c407b405fe98cac60b5d3c8f0d47f1e25d071a622

Tx prefix hash: 6eb52718a6c0925d4cc460e92b221823cdb1d2d4de4f24be5881a7b3efa97619
Tx public key: c8e987b47c133929f377719cd01268b99ff853601825c3503a8352abfba39cef
Timestamp: 1705743178 Timestamp [UCT]: 2024-01-20 09:32:58 Age [y:d:h:m:s]: 01:295:20:55:58
Block: 939324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470288 RingCT/type: yes/0
Extra: 01c8e987b47c133929f377719cd01268b99ff853601825c3503a8352abfba39cef0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bc977a97fdbf83b82ab346d9fccb2c3baa8a3acc68b5da8c2904f69af6238fc 0.600000000000 1397418 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": 939334, "vin": [ { "gen": { "height": 939324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bc977a97fdbf83b82ab346d9fccb2c3baa8a3acc68b5da8c2904f69af6238fc" } } ], "extra": [ 1, 200, 233, 135, 180, 124, 19, 57, 41, 243, 119, 113, 156, 208, 18, 104, 185, 159, 248, 83, 96, 24, 37, 195, 80, 58, 131, 82, 171, 251, 163, 156, 239, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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