Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0eaf88280fabc2c5a82dfd642c95d8875f27673034670aa64fd29343653b70f

Tx prefix hash: 3b37a84877e19da25d8ef5cb03b8ebd06dc467ccd67ca273d416cb82a418ed3b
Tx public key: 4f9f674c287306239488ff8a3db879b38ff2a57d72fece76a4d8509bf768f67c
Timestamp: 1732711196 Timestamp [UCT]: 2024-11-27 12:39:56 Age [y:d:h:m:s]: 00:348:12:28:26
Block: 1162838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246614 RingCT/type: yes/0
Extra: 014f9f674c287306239488ff8a3db879b38ff2a57d72fece76a4d8509bf768f67c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b121fcc5aa7419da955ab0f1223fdb7b9a7e78b7fa6055b285b93dd49594fe3b 0.600000000000 1648501 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": 1162848, "vin": [ { "gen": { "height": 1162838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b121fcc5aa7419da955ab0f1223fdb7b9a7e78b7fa6055b285b93dd49594fe3b" } } ], "extra": [ 1, 79, 159, 103, 76, 40, 115, 6, 35, 148, 136, 255, 138, 61, 184, 121, 179, 143, 242, 165, 125, 114, 254, 206, 118, 164, 216, 80, 155, 247, 104, 246, 124, 2, 17, 0, 0, 0, 1, 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