Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d345e6927f060de313cdb18e5a3980767b7b5e7ce06eb559aeb17f75ed3522d0

Tx prefix hash: 67db926ccd423f50a2821738db23741b2e3e5a4c1bb64df4e11f91edce28581c
Tx public key: 30315238f1af1c5fff4c701dc7fc96f7de859620641cb76bbf4a2b29236515a0
Timestamp: 1733223777 Timestamp [UCT]: 2024-12-03 11:02:57 Age [y:d:h:m:s]: 00:191:22:35:53
Block: 1167080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136975 RingCT/type: yes/0
Extra: 0130315238f1af1c5fff4c701dc7fc96f7de859620641cb76bbf4a2b29236515a00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aa70c549cb73c70e549c0ba060c63ca34f870e54739ea03299f5be77e4777af 0.600000000000 1652773 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": 1167090, "vin": [ { "gen": { "height": 1167080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aa70c549cb73c70e549c0ba060c63ca34f870e54739ea03299f5be77e4777af" } } ], "extra": [ 1, 48, 49, 82, 56, 241, 175, 28, 95, 255, 76, 112, 29, 199, 252, 150, 247, 222, 133, 150, 32, 100, 28, 183, 107, 191, 74, 43, 41, 35, 101, 21, 160, 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