Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3e80234e0bfc7c429114a41b4016b34639416c9f174a1f8caca3f6f1400bc66

Tx prefix hash: c0a139ca7239835a4c8d4a012c5a4d73bd97faba34134349843ea3eb576f3f34
Tx public key: fe9616d85321fe88ddd7dc4136e269c253ba95ab3b967a7da00b3addaf901354
Timestamp: 1635114794 Timestamp [UCT]: 2021-10-24 22:33:14 Age [y:d:h:m:s]: 04:007:14:03:37
Block: 359775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1042158 RingCT/type: yes/0
Extra: 01fe9616d85321fe88ddd7dc4136e269c253ba95ab3b967a7da00b3addaf90135402110000000e36fe6557000000000000000000

1 output(s) for total of 39.438145468000 dcy

stealth address amount amount idx
00: fc651add815607c09b56cb76e77c7bb9bf0fe940133cf314d1af7ef0da838197 39.438145468000 732504 of 0

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": 359785, "vin": [ { "gen": { "height": 359775 } } ], "vout": [ { "amount": 39438145468, "target": { "key": "fc651add815607c09b56cb76e77c7bb9bf0fe940133cf314d1af7ef0da838197" } } ], "extra": [ 1, 254, 150, 22, 216, 83, 33, 254, 136, 221, 215, 220, 65, 54, 226, 105, 194, 83, 186, 149, 171, 59, 150, 122, 125, 160, 11, 58, 221, 175, 144, 19, 84, 2, 17, 0, 0, 0, 14, 54, 254, 101, 87, 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