Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2103f233afb79380b5c221ecd2295437e9158ab041b5c52a493aa09b6f8a4f25

Tx prefix hash: d7a70441a4693fe2d7b254b73a0ee525d9ce4b46fe92db47199814e9dbc15a41
Tx public key: 09cf73b1360c688ff8649f2599c7ec31ef1e46cdfbde287d6111ea1b1b14729a
Timestamp: 1719942575 Timestamp [UCT]: 2024-07-02 17:49:35 Age [y:d:h:m:s]: 00:317:14:43:50
Block: 1057079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226967 RingCT/type: yes/0
Extra: 0109cf73b1360c688ff8649f2599c7ec31ef1e46cdfbde287d6111ea1b1b14729a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2974cd43f74554728c9e52d62100d74397ab3a236b7e92fd9f1d7dead02dba 0.600000000000 1527508 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": 1057089, "vin": [ { "gen": { "height": 1057079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2974cd43f74554728c9e52d62100d74397ab3a236b7e92fd9f1d7dead02dba" } } ], "extra": [ 1, 9, 207, 115, 177, 54, 12, 104, 143, 248, 100, 159, 37, 153, 199, 236, 49, 239, 30, 70, 205, 251, 222, 40, 125, 97, 17, 234, 27, 27, 20, 114, 154, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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