Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fdc50d21b743f267bd1c2fba127df2c081488acb06edafc5580e84202258403

Tx prefix hash: 9e5c5a72d1196f2c411c5c0c423161e03abb6bb10ea7120ef6c6cb8a223566de
Tx public key: d3330a07e421f03fda4b23a8b964faf0f8ef12e92655a956d33d2f5ccab3e50a
Timestamp: 1727216224 Timestamp [UCT]: 2024-09-24 22:17:04 Age [y:d:h:m:s]: 00:060:09:20:30
Block: 1117383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43163 RingCT/type: yes/0
Extra: 01d3330a07e421f03fda4b23a8b964faf0f8ef12e92655a956d33d2f5ccab3e50a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14823d3f7a08db84ed4c4744bc4b26a21c9c606e922c593b4ee70781d5372a54 0.600000000000 1598202 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": 1117393, "vin": [ { "gen": { "height": 1117383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14823d3f7a08db84ed4c4744bc4b26a21c9c606e922c593b4ee70781d5372a54" } } ], "extra": [ 1, 211, 51, 10, 7, 228, 33, 240, 63, 218, 75, 35, 168, 185, 100, 250, 240, 248, 239, 18, 233, 38, 85, 169, 86, 211, 61, 47, 92, 202, 179, 229, 10, 2, 17, 0, 0, 0, 4, 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