Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58467ba1ee2b7aef8f9f64e8f273b33b141e1cba60decf379affddea4f14a9df

Tx prefix hash: 468f7ae5c5b2992689c76c541847fa04dd3c8e5a70bd1cd48f47900c1431cbb8
Tx public key: 928308e3af35101cc3cc0deb1a837e2503377f5b03caee211843d427df33f793
Timestamp: 1722000500 Timestamp [UCT]: 2024-07-26 13:28:20 Age [y:d:h:m:s]: 01:105:08:12:23
Block: 1074141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333778 RingCT/type: yes/0
Extra: 01928308e3af35101cc3cc0deb1a837e2503377f5b03caee211843d427df33f79302110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee8a9f1ce81a20d523805a143aea8b64a28b31ca7e268c07f3ced058d1d01b8b 0.600000000000 1546654 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": 1074151, "vin": [ { "gen": { "height": 1074141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee8a9f1ce81a20d523805a143aea8b64a28b31ca7e268c07f3ced058d1d01b8b" } } ], "extra": [ 1, 146, 131, 8, 227, 175, 53, 16, 28, 195, 204, 13, 235, 26, 131, 126, 37, 3, 55, 127, 91, 3, 202, 238, 33, 24, 67, 212, 39, 223, 51, 247, 147, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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