Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4f5d5ce839d5dd7dab21c68eed2ac5f6c851deb8c4281791dff59620103799b

Tx prefix hash: 481ef6f77445f0cb9ac1c2b13830ae3af9736c1a38ac0c675ee6b77847265f5f
Tx public key: 48f12e6f6f7107186e6f7c7feb3fd0f17f470bcf1c5936570f9f6b5cef7015ea
Timestamp: 1716106940 Timestamp [UCT]: 2024-05-19 08:22:20 Age [y:d:h:m:s]: 00:327:14:32:06
Block: 1025288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234158 RingCT/type: yes/0
Extra: 0148f12e6f6f7107186e6f7c7feb3fd0f17f470bcf1c5936570f9f6b5cef7015ea0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8889a9a95178cd9172c1e0e4ff730e4ad39893a3850f2a59d0eb3441db79c02e 0.600000000000 1491681 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": 1025298, "vin": [ { "gen": { "height": 1025288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8889a9a95178cd9172c1e0e4ff730e4ad39893a3850f2a59d0eb3441db79c02e" } } ], "extra": [ 1, 72, 241, 46, 111, 111, 113, 7, 24, 110, 111, 124, 127, 235, 63, 208, 241, 127, 71, 11, 207, 28, 89, 54, 87, 15, 159, 107, 92, 239, 112, 21, 234, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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