Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb4883382eef3ec02d2f99a418a378ff8efd322bcedcfd59e4f912bc8e5feb38

Tx prefix hash: 6792e2a877c65cd605e813d0f53bc0bb1cd3f556293deb1e7dfcead28e1f9a20
Tx public key: 1beb3ddb953ed4b9d4228a265061d5ef78c4a4e81f86c32c8bbe8129d6f4be8e
Timestamp: 1764822668 Timestamp [UCT]: 2025-12-04 04:31:08 Age [y:d:h:m:s]: 00:025:03:14:49
Block: 1426029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17992 RingCT/type: yes/0
Extra: 011beb3ddb953ed4b9d4228a265061d5ef78c4a4e81f86c32c8bbe8129d6f4be8e021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2ed55ef6c46b6440de497e518827b2fc8ecf901af1a5c0ae7e5cee77844c835 0.600000000000 1914712 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": 1426039, "vin": [ { "gen": { "height": 1426029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2ed55ef6c46b6440de497e518827b2fc8ecf901af1a5c0ae7e5cee77844c835" } } ], "extra": [ 1, 27, 235, 61, 219, 149, 62, 212, 185, 212, 34, 138, 38, 80, 97, 213, 239, 120, 196, 164, 232, 31, 134, 195, 44, 139, 190, 129, 41, 214, 244, 190, 142, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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