Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8372fb98488d8a5f11f600b361a50cfc8dda771e1c3c67aaad36249da16742ec

Tx prefix hash: 93322c69bcb498c45a2550cb3fdc285a0591f1abe2faf2a7ad43fe846284dd9f
Tx public key: f73e8d6b010c6985119767b73b86e9a180b33df4e98a517c8c544afe9ed226e6
Timestamp: 1754559250 Timestamp [UCT]: 2025-08-07 09:34:10 Age [y:d:h:m:s]: 00:058:11:34:05
Block: 1342046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40791 RingCT/type: yes/0
Extra: 01f73e8d6b010c6985119767b73b86e9a180b33df4e98a517c8c544afe9ed226e6021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebee3a20fa0d27dba7ef916c0d114ef9358190106e8f054672cee111a3046449 0.600000000000 1829875 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": 1342056, "vin": [ { "gen": { "height": 1342046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebee3a20fa0d27dba7ef916c0d114ef9358190106e8f054672cee111a3046449" } } ], "extra": [ 1, 247, 62, 141, 107, 1, 12, 105, 133, 17, 151, 103, 183, 59, 134, 233, 161, 128, 179, 61, 244, 233, 138, 81, 124, 140, 84, 74, 254, 158, 210, 38, 230, 2, 17, 0, 0, 0, 2, 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