Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8b4f2c6358a3d1fe5c377ddee1a6d9f209e24fb6bfec223bd3ae249a1467cdb

Tx prefix hash: 4851d76f8cd51aa16f9d43b64761ae365731453318ea740c4f7b6f3840c2b3fc
Tx public key: 3440a346baa981809990eec02c19e9ccc59ccb73ea28a41b051a433430da9654
Timestamp: 1751570318 Timestamp [UCT]: 2025-07-03 19:18:38 Age [y:d:h:m:s]: 00:184:20:58:46
Block: 1318121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130470 RingCT/type: yes/0
Extra: 013440a346baa981809990eec02c19e9ccc59ccb73ea28a41b051a433430da9654021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 862a1200108ea8b8cbfeb455acbd407156056cc07b8128049c655f7849fa85bd 0.600000000000 1805794 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": 1318131, "vin": [ { "gen": { "height": 1318121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "862a1200108ea8b8cbfeb455acbd407156056cc07b8128049c655f7849fa85bd" } } ], "extra": [ 1, 52, 64, 163, 70, 186, 169, 129, 128, 153, 144, 238, 192, 44, 25, 233, 204, 197, 156, 203, 115, 234, 40, 164, 27, 5, 26, 67, 52, 48, 218, 150, 84, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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