Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820e2250b63ff75bfe06ce02ecba86821666f6601ea4ceb66c34841878c4fb71

Tx prefix hash: 969c5c13642bb1f424c3e3a37de9ce5b43e80e6faa9cdaa6e11a62415edab1df
Tx public key: 113441efa4e257c21a4cf752c86251de815c1a437df5db8c3b89a8980605f0af
Timestamp: 1676514578 Timestamp [UCT]: 2023-02-16 02:29:38 Age [y:d:h:m:s]: 01:278:02:02:38
Block: 697919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459660 RingCT/type: yes/0
Extra: 01113441efa4e257c21a4cf752c86251de815c1a437df5db8c3b89a8980605f0af02110000000174b6d784000000000000000000

1 output(s) for total of 2.988852956000 dcy

stealth address amount amount idx
00: 35094c007848cec8a233fe41ada890056f75bd7a57a7ee967e3cdf1153b167a5 2.988852956000 1141178 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": 697929, "vin": [ { "gen": { "height": 697919 } } ], "vout": [ { "amount": 2988852956, "target": { "key": "35094c007848cec8a233fe41ada890056f75bd7a57a7ee967e3cdf1153b167a5" } } ], "extra": [ 1, 17, 52, 65, 239, 164, 226, 87, 194, 26, 76, 247, 82, 200, 98, 81, 222, 129, 92, 26, 67, 125, 245, 219, 140, 59, 137, 168, 152, 6, 5, 240, 175, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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