Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeae648026834eabbb7c2f97a023f815d56d8e68d849f188701df49230e119c7

Tx prefix hash: b330721dd4826e53d1ca6e1225bdd834d51ded627f94d9fcb074d26af796f6d2
Tx public key: 83026feb6609287ddbc70dcebe3531d6dabd3fa26d3e6d202066f28a8035d97b
Timestamp: 1723947403 Timestamp [UCT]: 2024-08-18 02:16:43 Age [y:d:h:m:s]: 00:301:09:02:19
Block: 1090282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215217 RingCT/type: yes/0
Extra: 0183026feb6609287ddbc70dcebe3531d6dabd3fa26d3e6d202066f28a8035d97b021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e6d7e457a60c1d1b2a4668339292991073b01c442c3cb3b09470b3bae0cc0a9 0.600000000000 1564905 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": 1090292, "vin": [ { "gen": { "height": 1090282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e6d7e457a60c1d1b2a4668339292991073b01c442c3cb3b09470b3bae0cc0a9" } } ], "extra": [ 1, 131, 2, 111, 235, 102, 9, 40, 125, 219, 199, 13, 206, 190, 53, 49, 214, 218, 189, 63, 162, 109, 62, 109, 32, 32, 102, 242, 138, 128, 53, 217, 123, 2, 17, 0, 0, 0, 16, 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