Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d23a7e0186123dfc42c473853be858cbcccadf1dd9d788c96fa74387e94f09d

Tx prefix hash: b2eef140a022bec1e7cb57d058eb48880a8df3b71e8d6094ad8f2f5bfc46b513
Tx public key: f743f7e8498ecea6419a05371512deabb4f4f3ce749e852ffa77da16f3fbb4c5
Timestamp: 1724300380 Timestamp [UCT]: 2024-08-22 04:19:40 Age [y:d:h:m:s]: 00:228:12:29:05
Block: 1093219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163166 RingCT/type: yes/0
Extra: 01f743f7e8498ecea6419a05371512deabb4f4f3ce749e852ffa77da16f3fbb4c5021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1851b6a3fde922dbd7249910608b83e558f7ca68bb316972c7c6234f7c7fe9c9 0.600000000000 1568118 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": 1093229, "vin": [ { "gen": { "height": 1093219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1851b6a3fde922dbd7249910608b83e558f7ca68bb316972c7c6234f7c7fe9c9" } } ], "extra": [ 1, 247, 67, 247, 232, 73, 142, 206, 166, 65, 154, 5, 55, 21, 18, 222, 171, 180, 244, 243, 206, 116, 158, 133, 47, 250, 119, 218, 22, 243, 251, 180, 197, 2, 17, 0, 0, 0, 6, 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