Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43852a46414b1433a259b53bdc3d5256a8393c06c060259ba6896432798e22dc

Tx prefix hash: 56e370edc06915c273319aec2ab44c5778b98436a3738b21a210c0793f17b3cb
Tx public key: 01c5e7019ba6945b05c65a04530bf13ab19b4ed221c9776f8f0ba8b6be2e90ea
Timestamp: 1737865712 Timestamp [UCT]: 2025-01-26 04:28:32 Age [y:d:h:m:s]: 00:047:18:52:37
Block: 1205465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33979 RingCT/type: yes/0
Extra: 0101c5e7019ba6945b05c65a04530bf13ab19b4ed221c9776f8f0ba8b6be2e90ea021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba5801857503c5fe25ae54e4323e553e6ed942d6e929f0e9c0c4aa997d984da3 0.600000000000 1692162 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": 1205475, "vin": [ { "gen": { "height": 1205465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba5801857503c5fe25ae54e4323e553e6ed942d6e929f0e9c0c4aa997d984da3" } } ], "extra": [ 1, 1, 197, 231, 1, 155, 166, 148, 91, 5, 198, 90, 4, 83, 11, 241, 58, 177, 155, 78, 210, 33, 201, 119, 111, 143, 11, 168, 182, 190, 46, 144, 234, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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