Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ea22e65ab8c9cf5f013a1f53073897a5c3b4e413b974ca65c31cd36b19364f6

Tx prefix hash: 29fe6c5eb38624c8d5d74c784a311e83c61d1f872b4002de9c0415aeeff2c49d
Tx public key: a3e4baeba9ad1eda2c5595b8efe3084e8ddf27db256c57cb73f699b10da0e0f8
Timestamp: 1736464751 Timestamp [UCT]: 2025-01-09 23:19:11 Age [y:d:h:m:s]: 00:158:12:50:53
Block: 1193925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113025 RingCT/type: yes/0
Extra: 01a3e4baeba9ad1eda2c5595b8efe3084e8ddf27db256c57cb73f699b10da0e0f80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca9ddc05cb03161232aed2fc455e38c7f62c1ac3501168a6d12a39f41ddcee4d 0.600000000000 1680490 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": 1193935, "vin": [ { "gen": { "height": 1193925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca9ddc05cb03161232aed2fc455e38c7f62c1ac3501168a6d12a39f41ddcee4d" } } ], "extra": [ 1, 163, 228, 186, 235, 169, 173, 30, 218, 44, 85, 149, 184, 239, 227, 8, 78, 141, 223, 39, 219, 37, 108, 87, 203, 115, 246, 153, 177, 13, 160, 224, 248, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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