Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba9b0d78623893c50ba9e56e6def2188f62214bd7f0307a31c2423723bd5acb

Tx prefix hash: 4ae5628c659ba25e955bbf1f9df696ad4800aee9b60aa323eaf2d17d11f0f644
Tx public key: 4a8c53257e0214ae2b765aa5337290d3de05745936f3d18c10a315cfdb61f096
Timestamp: 1752405125 Timestamp [UCT]: 2025-07-13 11:12:05 Age [y:d:h:m:s]: 00:176:15:15:03
Block: 1324564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125029 RingCT/type: yes/0
Extra: 014a8c53257e0214ae2b765aa5337290d3de05745936f3d18c10a315cfdb61f096021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c6b2a88457a54f7796f79e89b4732ff7e05fb06a96ae1994eefa7560663fdec 0.600000000000 1812307 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": 1324574, "vin": [ { "gen": { "height": 1324564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c6b2a88457a54f7796f79e89b4732ff7e05fb06a96ae1994eefa7560663fdec" } } ], "extra": [ 1, 74, 140, 83, 37, 126, 2, 20, 174, 43, 118, 90, 165, 51, 114, 144, 211, 222, 5, 116, 89, 54, 243, 209, 140, 16, 163, 21, 207, 219, 97, 240, 150, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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