Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a238a2e02a39e31a7824d52e0ec4d4d8e62153eaff29a834a07f8fda297c3a1e

Tx prefix hash: 073ead1483267af53f719ffaceb2e9a88ebae0579020ff167e35e24462a62fa3
Tx public key: 0125139e4a833a4e99f4eb06b646a7fb05092a763f247a388eb9fd9e529252f4
Timestamp: 1723896528 Timestamp [UCT]: 2024-08-17 12:08:48 Age [y:d:h:m:s]: 00:249:14:57:03
Block: 1089868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178280 RingCT/type: yes/0
Extra: 010125139e4a833a4e99f4eb06b646a7fb05092a763f247a388eb9fd9e529252f4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1cdf27844523d04e5eb108744eca82f06fd23ad6a867aa873a306fef4306e23 0.600000000000 1564491 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": 1089878, "vin": [ { "gen": { "height": 1089868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1cdf27844523d04e5eb108744eca82f06fd23ad6a867aa873a306fef4306e23" } } ], "extra": [ 1, 1, 37, 19, 158, 74, 131, 58, 78, 153, 244, 235, 6, 182, 70, 167, 251, 5, 9, 42, 118, 63, 36, 122, 56, 142, 185, 253, 158, 82, 146, 82, 244, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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