Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78288767f46cb5a46f8eb451579874e78bbcdfb240e66472e44672fde12ed6de

Tx prefix hash: 2c10771670585c0a06ea6d8e81ad05f2254b4f998431065322f9f082dcd460bc
Tx public key: 1eb87f531af0f2205a6a0ff8ae5c1256bdb80969cd803881414c015d1f2f7cac
Timestamp: 1749168649 Timestamp [UCT]: 2025-06-06 00:10:49 Age [y:d:h:m:s]: 00:235:23:55:11
Block: 1298826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166264 RingCT/type: yes/0
Extra: 011eb87f531af0f2205a6a0ff8ae5c1256bdb80969cd803881414c015d1f2f7cac02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8d833a1eaa9dc60dd0f9cd8d6e6753cf96f81f9758c03bf63d1319af4cd34bc 0.600000000000 1786357 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": 1298836, "vin": [ { "gen": { "height": 1298826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8d833a1eaa9dc60dd0f9cd8d6e6753cf96f81f9758c03bf63d1319af4cd34bc" } } ], "extra": [ 1, 30, 184, 127, 83, 26, 240, 242, 32, 90, 106, 15, 248, 174, 92, 18, 86, 189, 184, 9, 105, 205, 128, 56, 129, 65, 76, 1, 93, 31, 47, 124, 172, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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